Skip Headers

Oracle® Database Error Messages 10g Release 2 (10.2) Part Number B14219-01 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next

# 32 OCI-00601 to OCI-31199

OCI-00601: cleanup lock conflict
  Cause: PMON process runs into lock conflict trying to recover processes.
  Action: This is trapped internally, no action necessary.

OCI-00602: internal programming exception
  Cause: Internal programming exception.
  Action: Report as a bug. Caution: The following error code is not relocatable.

OCI-00972: identifier is too long
  Cause: An identifier with more than 30 characters was specified.
  Action: Specify at most 30 characters.

OCI-01841: (full) year must be between -4713 and +9999, and not be 0
  Cause: Illegal year entered
  Action: Input year in the specified range

OCI-01854: julian date must be between 1 and 5373484
  Cause: An invalid Julian date was entered.
  Action: Enter a valid Julian date between 1 and 5373484.

OCI-01858: a non-numeric character was found where a numeric was expected
  Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model.
  Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.

OCI-01859: a non-alphabetic character was found where an alphabetic was expected
  Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a letter where a letter was required by the format model.
  Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.

OCI-01861: literal does not match format string
  Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading whitespace). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra whitespace.
  Action: Correct the format string to match the literal.

OCI-01862: wrong number of digits for this format item
  Cause: The number of digits used for this format item is not equal to the number necessary for this format when specifying Format eXact ("FX") for this item.
  Action: Fill out this format item with leading zeros to the number necessary for this format. (This is generally the number of characters in the format code--DD needs 2 digits, for example. The exceptions are HH24 & HH12, which both need 2, and J, which needs 9.)

OCI-01864: the date is out of range for the current calendar
  Cause: Your calendar doesn't extend to the specified date.
  Action: Specify a date which is legal for this calendar.

OCI-01865: not a valid era
  Cause: Era input does not match a known era.
  Action: Provide a valid era on input.

OCI-01898: too many precision specifiers
  Cause: While trying to truncate or round dates, extra data was found in the date format picture
  Action: Check the syntax of the date format picture and retry.

OCI-02083: database name has illegal character 'string'
  Cause: Supplied database name can contain only A-Z, 0-9, '_', '#', '$' '.' and '@' characters.
  Action: none

OCI-02084: database name is missing a component
  Cause: Supplied database name cannot contain a leading '.', trailing '.' or '@', or two '.' or '@' in a row.
  Action: none

OCI-04020: deadlock detected while trying to lock object string string string string string
  Cause: While trying to lock a library object, a deadlock is detected.
  Action: Retry the operation later.

OCI-04021: timeout occurred while waiting to lock object string string string string string
  Cause: While waiting to lock a library object, a timeout is occurred.
  Action: Retry the operation later.

OCI-04022: nowait requested, but had to wait to lock dictionary object
  Cause: Had to wait to lock a library object during a nowait request.
  Action: Retry the operation later.

OCI-04028: cannot generate diana for object string string string string string
  Cause: Cannot generate diana for an object because of lock conflict.
  Action: Please report this error to your support representative.

OCI-04029: error ORA-string occurred when querying string string string
  Cause: The table or view being queried might be missing. The error number indicates the error.
  Action: Fix the error.

OCI-04030: out of process memory when trying to allocate string bytes (string,string)
  Cause: Operating system process private memory has been exhausted
  Action: none

OCI-04031: unable to allocate string bytes of shared memory ("string","string","string")
  Cause: More shared memory is needed than was allocated in the shared pool.
  Action: Either use the dbms_shared_pool package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the init.ora parameter "shared_pool_size".

OCI-04054: database link string does not exist
  Cause: During compilation of a PL/SQL block, an attempt was made to use a non-existent database link.
  Action: Either use a different database link or create the database link.

OCI-04060: insufficient privileges to execute string
  Cause: Attempt to execute a stored procedure without sufficient privileges.
  Action: Get necessary privileges.

OCI-04061: existing state of string has been invalidated
  Cause: Attempt to resume the execution of a stored procedure using the existing state which has become invalid or inconsistent with the stored procedure because the procedure has been altered or dropped.
  Action: Try again; this error should have caused the existing state of all packages to be re-initialized.

OCI-04062: timestamp of string has been changed
  Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a timestamp that is different from the current timestamp of the procedure.
  Action: Recompile the caller in order to pick up the new timestamp.

OCI-04063: %s has errors
  Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table.
  Action: Fix the errors and/or create referenced objects as necessary.

OCI-04064: not executed, invalidated string
  Cause: Attempt to execute a stored procedure that has been invalidated.
  Action: Recompile it.

OCI-04065: not executed, altered or dropped string
  Cause: Attempt to execute a stored procedure that has been altered or dropped thus making it not callable from the calling procedure.
  Action: Recompile its dependents.

OCI-04066: non-executable object, string
  Cause: Attempt to execute a non-procedure.
  Action: Make sure that a correct name is given.

OCI-04067: not executed, string does not exist
  Cause: Attempt to execute a non-existent stored procedure.
  Action: Make sure that a correct name is given.

OCI-04068: existing state of packagesstring string string has been discarded
  Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure.
  Action: Try again after proper re-initialization of any application's state.

OCI-19200: Invalid column specification
  Cause: All input arguments must be valid columns
  Action: Specify a valid list of columns

OCI-19201: Datatype not supported
  Cause: The particular datatype is not supported in the XMLGEN operator
  Action: Specify only supported datatypes as arguments to the XMLGEN operator

OCI-19202: Error occurred in XML processingstring
  Cause: An error occurred when processing the XML function
  Action: Check the given error message and fix the appropriate problem

OCI-19203: Error occurred in DBMS_XMLGEN processingstring
  Cause: An error occurred when processing the DBMS_XMLGEN functions
  Action: Check the given error message and fix the appropriate problem

OCI-19204: Non-scalar value 'string' is marked as XML attribute
  Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by '@'. In this case, a non-scalar value was prefixed with '@'
  Action: Remove the '@' sign, or make the value a scalar.

OCI-19205: Attribute 'string' qualifies a non-scalar value in the select list
  Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.
  Action: Remove the '@' sign, or make the previous value a scalar.

OCI-19206: Invalid value for query or REF CURSOR parameter
  Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR.
  Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR.

OCI-19207: scalar parameter string of XMLELEMENT cannot have an alias.
  Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.
  Action: Remove the AS clause of the scalar element.

OCI-19208: parameter string of function string must be aliased
  Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.
  Action: Specify an alias for the expression using the AS clause.

OCI-19209: invalid or unsupported formatting argument
  Cause: An invalid or unsupported formatting argument was supplied
  Action: Change the formatting argument to legal supported values

OCI-19210: column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table.
  Action: Change the column specified to be a column in the table

OCI-19211: column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
  Cause: The column specified using setKeyColumn() was a non-scalar type column.
  Action: Change the column specified to be a scalar column in the table

OCI-19212: no key columns specified before call to DBMS_XMLSTORE.updateXML()
  Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML.
  Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns

OCI-21300: objects option not installed
  Cause: The objects option is not installed at this site. Object types and other object features are, therefore, unavailable.
  Action: Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle sales representative if the objects option needs to be purchased.

OCI-21301: not initialized in object mode
  Cause: This function requires the oci process to be initialized in object mode.
  Action: Specify OCI_OBJECT mode when calling OCIInitialize().

OCI-21500: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  Cause: This is the generic error number for the OCI environment (client-side) internal errors. This indicates that the OCI environment has encountered an exceptional condition.
  Action: Report as a bug - the first argument is the internal error number.

OCI-21501: program could not allocate memory
  Cause: The operating system has run out of memory.
  Action: Take action to make more memory available to the program.

OCI-21503: program terminated by fatal error
  Cause: A program is in an unrecoverable error state.
  Action: Report as a bug.

OCI-21520: database server driver not installed
  Cause: User attempted to access a database server through an object-mode OCI environment but the necessary driver for supporting such access to the database server is not installed or linked in.
  Action: Check if the driver corresponding to the database server has been installed/linked in and entered in the server driver table.

OCI-21521: exceeded maximum number of connections in OCI (object mode only)
  Cause: User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode.
  Action: Close some of existing and unused connections before opening more connections.

OCI-21522: attempted to use an invalid connection in OCI (object mode only)
  Cause: User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to dereference a REF obtained from a connection which has been terminated.
  Action: Ensure that the connection exists and is still valid.

OCI-21523: functionality not supported by the server (object mode only)
  Cause: User attempted to use a functionality that the server does not support.
  Action: Upgrade the server

OCI-21524: object type mismatch
  Cause: The object type of the object is different from what is specified.
  Action: Check the type of the object and correct it.

OCI-21525: attribute number (or collection element at index) string violated its constraints
  Cause: Attribute value or collection element value violated its constraint.
  Action: Change the value of the attribute or collection element such that it meets its constraints. The constraints are specified as part of the attribute or collection element's schema information.

OCI-21526: initialization failed
  Cause: The initialization sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value.
  Action: Check that all NLS environment variables are well-formed.

OCI-21527: internal OMS driver error
  Cause: A process has encountered an exceptional condition. This is the generic internal error number for Oracle object management services exceptions.
  Action: Report this as a bug to Oracle Support Services.

OCI-21560: argument string is null, invalid, or out of range
  Cause: The argument is expecting a non-null, valid value but the argument value passed in is null, invalid, or out of range. Examples include when the LOB/FILE positional or size argument has a value outside the range 1 through (4GB - 1), or when an invalid open mode is used to open a file, etc.
  Action: Check your program and correct the caller of the routine to not pass a null, invalid or out-of-range argument value.

OCI-21600: path expression too long
  Cause: The path expression that is supplied by the user is too long. The path expression is used to specify the position of an attribute in an object. This error occurs when one of the intermediate elements in the path expression refers to an attribute of a built-in type. Thus, the OCI function cannot proceed on to process the rest of the elements in the path expression.
  Action: User should pass in the correct path expression to locate the attribute.

OCI-21601: attribute is not an object
  Cause: The user attempts to perform an operation (that is valid only for an object) to an attribute of a built-in type. An example of such an illegal operation is to dynamically set a null structure to an attribute of a built-in type.
  Action: User should avoid performing such operation to an attribute of built-in type.

OCI-21602: operation does not support the specified typecode
  Cause: The user attempts to perform an operation that does not support the specified typecode.
  Action: User should use the range of valid typecodes that are supported by this operation.

OCI-21603: property id [string] is invalid
  Cause: The specified property id is invalid.
  Action: User should specify a valid property id. Valid property ids are enumerated by OCIObjectPropId.

OCI-21604: property [string] is not a property of transient or value instances
  Cause: Trying to get a property which applies only to persistent objects.
  Action: User should check the lifetime and only get this property for persistent objects.

OCI-21605: property [string] is not a property of value instances
  Cause: Trying to get a property which applies only to persistent and transient objects.
  Action: User should check the lifetime and only get this property for persistent and transient objects.

OCI-21606: can not free this object
  Cause: Trying to free an object that is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified.
  Action: Either flush the persistent object or set the flag to OCI_OBJECTFREE_FORCE

OCI-21607: memory cartridge service handle not initialized
  Cause: Attempt to use the handle without initializing it.
  Action: Initialize the memory cartridge service handle.

OCI-21608: duration is invalid for this function
  Cause: Attempt to use a duration not valid for this function.
  Action: Use a valid duration - a previously created user duration or OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout duration or external procedure duration, use OCIExtProcAllocCallMemory.

OCI-21609: memory being resized without being allocated first
  Cause: Attempt to resize memory without allocating it first.
  Action: Allocate the memory first before resizing it.

OCI-21610: size [string] is invalid
  Cause: Attempt to resize memory with invalid size.
  Action: Pass in a valid size (must be a positive integer).

OCI-21611: key length [string] is invalid
  Cause: Attempt to use an invalid key length.
  Action: Key length is invalid and valid range is 0 to 64

OCI-21612: key is already being used
  Cause: Attempt to use a key that is already used.
  Action: Use a new key that is not yet being used.

OCI-21613: key does not exist
  Cause: Attempt to use a non-existent key
  Action: Use a key that already exists.

OCI-21700: object does not exist or is marked for delete
  Cause: User attempted to perform an inappropriate operation to an object that is non-existent or marked for delete. Operations such as pinning, deleting and updating cannot be applied to an object that is non-existent or marked for delete.
  Action: User needs to re-initialize the reference to reference an existent object or the user needs to unmark the object.

OCI-21701: attempt to flush objects to different servers
  Cause: User attempted to flush objects to different servers in one function call. These objects are obtained by calling a callback functions provided by the program.
  Action: User should avoid performing such operation.

OCI-21702: object is not instantiated or has been de-instantiated in cache
  Cause: User attempted to perform an inappropriate operation to a transient object that is not instantiated in the object cache. Operations that cannot be applied to a not-instantiated transient object include deleting or pinning such an object.
  Action: User should check their code to see if they are performing such an operation without instantiating the object first, or performing such an operation after the allocation duration of the object has expired.

OCI-21703: cannot flush an object that is not modified
  Cause: See the error message.
  Action: The object should not be flushed.

OCI-21704: cannot terminate cache or connection without flushing first
  Cause: See the error message.
  Action: The transaction should be aborted or committed before terminating the cache or connection.

OCI-21705: service context is invalid
  Cause: The service context that is supplied by the user is not valid.
  Action: User needs to establish the service context.

OCI-21706: duration does not exist or is invalid
  Cause: The duration number that is supplied by the user is not valid.
  Action: User needs to establish the duration or use a correct predefined duration.

OCI-21707: pin duration is longer than allocation duration
  Cause: The pin duration supplied by the user is longer than the allocation duration. This affects operations such as pinning and setting default parameters.
  Action: User should use a shorter pin duration or use the null duration.

OCI-21708: inappropriate operation on a transient object
  Cause: User attempted to perform an inappropriate operation on a transient object. Operations that cannot be applied to a transient object include flushing and locking.
  Action: User should avoid performing such operation on a transient object.

OCI-21709: cannot refresh an object that has been modified
  Cause: User attempted to refresh an object that has been marked for delete, update or insert (new).
  Action: User should unmark the object before refreshing it.

OCI-21710: argument is expecting a valid memory address of an object
  Cause: The object memory address that is supplied by the user is invalid. The user may have passed in a bad memory address to a function that is expecting a valid memory address of an object.
  Action: User should pass in a valid memory address of an object to the function.

OCI-21779: duration not active
  Cause: User is trying to use a duration that has been terminated.
  Action: User should avoid performing such operation.

OCI-22053: overflow error
  Cause: This operation's result is above the range of Oracle number.
  Action: Decrease the input value(s) so that the result is in the range of Oracle number.

OCI-22054: underflow error
  Cause: This operation's result is below the range of Oracle number.
  Action: Increase the input value(s) so that the result is in the range of Oracle number.

OCI-22055: unknown sign flag value [string]
  Cause: Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED.
  Action: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign flag.

OCI-22056: value [string] is divided by zero
  Cause: Given value is divied by zero.
  Action: Modify divisor value to be non-zero.

OCI-22057: bad integer length [string]
  Cause: The length of the integer (ie number of bytes) to be converted to or from an Oracle number is invalid.
  Action: Use integer length 1, 2, 4 or 8 bytes only.

OCI-22059: buffer size [string] is too small - [string] is needed
  Cause: The buffer to hold the resulting text string is too small.
  Action: Provide a buffer of the required size.

OCI-22060: argument [string] is an invalid or uninitialized number
  Cause: An invalid or uninitialized number is passed in.
  Action: Use a valid number. To initialize number call OCINumberSetZero().

OCI-22061: invalid format text [string]
  Cause: The numeric format string for converting characters to or from an Oracle number is invalid.
  Action: Use valid format string as documented in OCI Programmer's Guide.

OCI-22062: invalid input string [string]
  Cause: The text string for converting to numbers is invalid.
  Action: Use a valid input string as documented in OCI Programmer's Guide.

OCI-22063: reading negative value [string] as unsigned
  Cause: Attempt to convert a negative number to an unsigned integer.
  Action: Use the sign flag ORLTSB to convert a signed number.

OCI-22064: invalid NLS parameter string [string]
  Cause: The NLS parameter string for converting characters to or from an Oracle number is invalid.
  Action: Use valid format string as documented in OCI Programmer's Guide.

OCI-22065: number to text translation for the given format causes overflow
  Cause: Rounding done due to the given string format causes overflow.
  Action: Change the format such that overflow does not occur.

OCI-22130: buffer size [string] is less than the required size [string]
  Cause: The size of the buffer into which the hexadecimal REF string is to be written is too small.
  Action: Provide a buffer of the required size.

OCI-22131: hexadecimal string length is zero
  Cause: The given hexadecimal string length must be greater than zero.
  Action: Specify a length greater than zero.

OCI-22132: hexadecimal string does not correspond to a valid REF
  Cause: The given hexadecimal string is invalid.
  Action: Provide a valid hexadecimal string which was previously returned by a call to OCIRefToHex().

OCI-22140: given size [string] must be in the range of 0 to [string]
  Cause: The given resize size is invalid.
  Action: Ensure that the given size is in the required range.

OCI-22150: variable-length array has not been initialized
  Cause: An un-initialized variable-length array is being operated upon.
  Action: Initialize the variable-length array prior to calling this function.

OCI-22151: cannot resize non-zero variable-length array to zero elements
  Cause: Trying to resize a non-zero variable-length array to 0 elements.
  Action: Specify a non-zero size.

OCI-22152: destination variable-length array is not initialized
  Cause: The variable-length array on the right-hand-side of an assignment or the destination array of an append is not initialized.
  Action: Initialize the destination variable-length array prior to calling this function.

OCI-22153: source variable-length array is not initialized
  Cause: The variable-length array on the left-hand-side of an assignment or the source array of an append is not initialized.
  Action: Initialize the destination variable-length array prior to calling this function.

OCI-22160: element at index [string] does not exist
  Cause: Collection element at the given index does not exist.
  Action: Specify the index of an element which exists.

OCI-22161: type code [string] is not valid
  Cause: Given type code is not valid.
  Action: Use one of the typecodes enumerated in OCITypeCode.

OCI-22162: element at index [string] has been previously deleted
  Cause: Trying to delete a non-existent collection element.
  Action: Check for the existence of the element prior to calling this function.

OCI-22163: left hand and right hand side collections are not of same type
  Cause: Left hand and right side collections are not of same type.
  Action: Ensure that the same collection type is passed for both left hand and right hand side of this function.

OCI-22164: delete element operation is not allowed for variable-length array
  Cause: Trying to delete an element of a variable-length array.
  Action: Ensure that the collection is not a variable-length array prior to calling this function.

OCI-22165: given index [string] must be in the range of [string] to [string]
  Cause: Given index is not in the required range.
  Action: Ensure that the given index is in the required range.

OCI-22166: collection is empty
  Cause: Given collection is empty.
  Action: Test if collection is empty prior to invoking this function.

OCI-22167: given trim size [string] must be less than or equal to [string]
  Cause: Given trim size is greater than the current collection size.
  Action: Ensure that the given size is less than or equal to the collection size prior to calling this function.

OCI-22275: invalid LOB locator specified
  Cause: There are several causes: (1) the LOB locator was never initialized; (2) the locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator; (4) trying to update the LOB in a trigger body -- LOBs in trigger bodies are read only.
  Action: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value.

OCI-22276: invalid locator for LOB buffering
  Cause: There are several causes: (1) the locator was never enabled for buffering (2) it is not an updated locator but is being used for a write/flush operation
  Action: For (1) enable the locator for buffering; (2) ensure that only an updated locator is used for a LOB update operation

OCI-22277: cannot use two different locators to modify the same LOB
  Cause: LOB buffering is enabled and an attempt was made to modify the LOB using two different LOB locators.
  Action: When using LOB buffering, modify the LOB through one LOB locator only.

OCI-22278: must update the LOB only through the LOB buffers
  Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the buffer pool. Thus, updating the LOB through means other than the LOB buffers is not allowed.
  Action: Update the LOB through the LOB buffers using the locator that has LOB buffering enabled. If this operation is required, buffers associated with this LOB should either be flushed as necessary or buffering should be disabled. Once this is done, reissue the command.

OCI-22279: cannot perform operation with LOB buffering enabled
  Cause: The operation attempted is not allowed when LOB buffering is enabled.
  Action: If the operation is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the command.

OCI-22280: no more buffers available for operation
  Cause: There are two causes: (1) All buffers in the buffer pool have been used up by previous operations (2) Attempt to flush a LOB without any previous buffered update operations.
  Action: For (1), flush the LOB(s) through the locator that is being used to update the LOB. For (2), write to the LOB through a locator enabled for buffering before attempting to flush buffers.

OCI-22281: cannot perform operation with an updated locator
  Cause: The input locator has buffering enabled and was used to update the LOB value through the LOB buffering subsystem. The modified buffer has not been flushed since the write that was performed by the the input locator; thus, the input locator is considered an updated locator. Updated locators cannot be the source of a copy operation. Only one locator per LOB may be used to modify the LOB value through the LOB buffering subsystem.
  Action: Depending on whether the modifications made through the input locator to the LOB buffering subsystem should be written to the server, either flush the buffer to write the modifications, or, disable buffering on the locator to discard the modifications. Then, reissue the command.

OCI-22282: non-contiguous append to a buffering enabled LOB not allowed
  Cause: The buffered write operation has an input offset value more than one byte or character past the end of the LOB.
  Action: Specify an input offset value which is exactly one character or byte greater than the length of the LOB that you are attempting to update through a buffered write operation.

OCI-22285: non-existent directory or file for string operation
  Cause: Attempted to access a directory that does not exist, or attempted to access a file in a directory that does not exist.
  Action: Ensure that a system object corresponding to the specified directory exists in the database dictionary, or make sure the name is correct.

OCI-22286: insufficient privileges on directory or file to perform string operation
  Cause: The user does not have the necessary access privileges on the directory alias and/or the file for the operation.
  Action: Ask the database/system administrator to grant the required privileges on the directory alias and/or the file.

OCI-22287: invalid or modified directory occurred during string operation
  Cause: The directory alias used for the current operation is not valid if being accessed for the first time, or has been modified by the DBA since the last access.
  Action: If you are accessing this directory for the first time, provide a valid directory name. If you have been already successful in opening a file under this directory before this error occured, then close the file and retry the operation with a valid directory alias as modified by your DBA. Oracle recommends that directories should be modified only during quiescent periods.

OCI-22288: file operation string failed string
  Cause: The operation attempted on the file failed.
  Action: See the next error message for more detailed information. Also, verify that the file exists and that the necessary privileges are set for the specified operation. If the error still persists, report the error to the DBA.

OCI-22289: cannot perform string operation on an unopened file
  Cause: The file is not open for the required operation to be performed.
  Action: Check that the current operation is preceded by a successful file open operation.

OCI-22290: operation would exceed the maximum number of opened files
  Cause: The number of open files has reached the maximum limit.
  Action: Close some of the opened files and retry the operation.

OCI-22303: type "string"."string" not found
  Cause: The user is trying to obtain information for a type that cannot be found.
  Action: Check that the schema is correct and that the type has been created correctly.

OCI-22305: attribute/method/parameter "string" not found
  Cause: Type element with the given name is not found in the type.
  Action: Check to make sure that the type element exists.

OCI-22306: type "string"."string" already exists
  Cause: The user is trying to create a type that already exists.
  Action: Check to make sure that the type has not been created prior to this.

OCI-22307: type to alter is not a user-defined type
  Cause: The user is trying to alter a built-in type.
  Action: Check to make sure that only user-defined types are being altered.

OCI-22309: attribute with name "string" already exists
  Cause: The user is attempting to create an object type where more than one attributes have the same name.
  Action: Check to make sure that all attribute names are unique.

OCI-22311: type for attribute "string" does not exist
  Cause: The type of the attribute does not exist.
  Action: No types were created/modified for this DDL transaction. Redo the DDL transaction and add the creation of the attribute's type in the DDL transaction.

OCI-22313: cannot use two versions of the same type "string"
  Cause: The version of this type conflicts with the version of this type used by another library that was linked in with the application. An application may only use one version of a type.
  Action: Check that the libraries being linked with this application and use the same versions of the type.

OCI-22314: method information mismatch in ALTER TYPE
  Cause: The number of methods or the method signature do not match that of the original type declaration. This is not supported.
  Action: Make sure the method signature stay identical for the previously declared method. Do not drop existing methods.

OCI-22315: type "string" does not contain a map or order function
  Cause: The input type does not contain a map or order function so one cannot be returned.
  Action: Add a map or order function to the type or catch this error.

OCI-22316: input type is not a collection type
  Cause: The user is trying to obtain information for collection types on a non-named collection type.
  Action: Use a named collection type for the function.

OCI-22317: typecode number is not legal as a number type
  Cause: The user is trying to use a number typecode that is not valid.
  Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT, OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL.

OCI-22318: input type is not an array type
  Cause: The user is trying to obtain the number of elements for a non-array type.
  Action: Pass in only a named collection type which is an array.

OCI-22319: type attribute information altered in ALTER TYPE
  Cause: The type attribute information does not match that of the original type declaration when altering type. Attributes cannot be altered during ALTER TYPE. Only new methods can be added.
  Action: Check that all type alterations are legal.

OCI-22321: method does not return any result
  Cause: OCITypeResult() was called on a method that does not return any results.
  Action: Check that you are passing in the correct method descriptor, or that your method creation was done correctly.

OCI-22337: the type of accessed object has been evolved
  Cause: The type of the accessed object has been altered and the client's object is based on an earlier type definition.
  Action: The user needs to exit application and modify application to accommodate the type change. From SQL/PLUS, reconnect and resubmit statement.

OCI-22369: invalid parameter encountered in method string
  Cause: An invalid parameter is being passed to this method of SYS.RowType or SYS.RowSet.
  Action: Check the parameters being passed to this method and make sure that the parameters are allowed.

OCI-22370: incorrect usage of method string
  Cause: This method of SYS.RowType or SYS.RowSet is being used inappropriately.
  Action: Check the documentation for correct usage.

OCI-22600: encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  Cause: Production Oracle8 (8.0.3 and beyond) encounters some VARRAY data which was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY data.
  Action: Delete the VARRAY data from the table by dropping the table, deleting the rows, or nulling out the VARRAY columns, and then re-insert the VARRAY data. There is no provided script or tool to help automate this conversion.

OCI-22601: pickler TDS context [string] is not initialized
  Cause: Attempt to use the pickler TDS context without initializing it.
  Action: Use OCIPicklerTdsCtxInit to initialize the context.

OCI-22602: pickler TDS handle [string] is not well-formed
  Cause: Attempt to use the pickler TDS handle without initializing/ constructing it.
  Action: Use OCIPicklerTdsInit to initialize the handle before it is constructed. Use OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed.

OCI-22603: cannot add an attribute to the already generated TDS handle
  Cause: Attempt to add an attribute to the already constructed TDS.
  Action: Use a TDS handle that is initialized but not yet constructed.

OCI-22604: TDS handle already generated
  Cause: Attempt to geneate TDS that is already genearated.
  Action: Use a TDS handle that is initialized but not yet generated.

OCI-22605: FDO handle [string] is not initialized
  Cause: Attempt to use an uninitialized FDO handle.
  Action: Use OCIPicklerFdoInit to initialize FDO handle".

OCI-22606: pickler image handle [string] is not well-formed
  Cause: Attempt to use the image handle without initializing/ constructing it.
  Action: Use OCIPicklerImageInit to initialize the handle before it is constructed. Use OCIPicklerImageGenerate to generate the image before its attributes can be accessed.

OCI-22607: image handle already generated
  Cause: Attempt to geneate image that is already genearated.
  Action: Use a image handle that is initialized but not yet generated.

OCI-22608: cannot add an attribute to the already generated image handle
  Cause: Attempt to add an attribute to the already constructed image.
  Action: Use an image handle that is initialized but not yet constructed.

OCI-22609: error string during initialization of FDO
  Cause: Error during FDO initialization.
  Action: Take an action based on the specified error.

OCI-22626: Type Mismatch while constructing or accessing OCIAnyData
  Cause: Type supplied is not matching the type of the AnyData. If piece wise construction or access is being attempted, the type supplied is not matching the type of the current attribute.
  Action: Make sure the type supplied matches the type of object to to be constucted or accessed.

OCI-22975: cannot create a PRIMARY KEY-based REF to this object view
  Cause: The object view specified in the MAKE_REF function does not have a PRIMARY KEY-based object identifier. A PRIMARY KEY-based REF cannot be created for such a view.
  Action: Specify an object view that has a PRIMARY KEY-based object identifier in the MAKE_REF function.

OCI-22976: incorrect number of arguments to MAKE_REF
  Cause: Number of arguments for MAKE_REF is different from the number of PRIMARY KEY attributes of the object view.
  Action: Specify all the necessary arguments for MAKE_REF.

OCI-30100: internal error [number]
  Cause: An internal error has occurred.
  Action: Contact Oracle Worldwide Support and report the error.

OCI-30101: unknown parameter name 'string'
  Cause: You have misspelled the parameter name.
  Action: Spell the parameter name correctly.

OCI-30102: 'string' is not in the legal range for 'string'
  Cause: The value of the parameter is not within the legal range.
  Action: Refer to the manual for the allowable values for this parameter.

OCI-30103: 'string' contains an illegal integer radix for 'string'
  Cause: An illegal integer radix specification was found.
  Action: Only 'd', 'h', 'D', and 'H' may be used as radix specifications.

OCI-30104: 'string' is not a legal integer for 'string'
  Cause: The value is not a valid integer.
  Action: Specify only valid integers for this parameter.

OCI-30105: 'string' is not a legal boolean for 'string'
  Cause: The value is not a valid boolean.
  Action: Refer to the manual for allowable boolean values.

OCI-30106: reserved for future use
  Cause: None.
  Action: None.

OCI-30107: parameter name abbreviation 'string' is not unique
  Cause: The abbreviation given was not unique.
  Action: Use a longer abbreviation to make the parameter name unique.

OCI-30108: invalid positional parameter value 'string'
  Cause: An invalid positional parameter value has been entered.
  Action: Remove the invalid positional parameter.

OCI-30109: could not open parameter file 'string'
  Cause: The parameter file does not exist.
  Action: Create an appropriate parameter file.

OCI-30110: syntax error at 'string'
  Cause: A syntax error was detected.
  Action: Change the input so that the correct syntax is used.

OCI-30111: no closing quote for value 'string'
  Cause: A quoted string was begun but not finished.
  Action: Put a closing quote in the proper location.

OCI-30112: multiple values not allowed for parameter 'string'
  Cause: You attempted to specify multiple values for a parameter which can take only one value.
  Action: Do not specify more than one value for this parameter.

OCI-30113: error when processing file 'string'
  Cause: A problem occurred when processing this file.
  Action: Examine the additional error messages and correct the problem.

OCI-30114: error when processing from command line
  Cause: A problem occurred when processing the command line.
  Action: Examine the additional error messages and correct the problem.

OCI-30115: error when processing an environment variable
  Cause: A problem occurred when processing an environment variable.
  Action: Examine the additional error messages and correct the problem.

OCI-30116: syntax error at 'string' following 'string'
  Cause: A syntax error was detected.
  Action: Change the input so that the correct syntax is used.

OCI-30117: syntax error at 'string' at the start of input
  Cause: A syntax error was detected.
  Action: Change the input so that the correct syntax is used.

OCI-30118: syntax error at 'string' at the end of input
  Cause: A syntax error was detected.
  Action: Change the input so that the correct syntax is used.

OCI-30119: unable to obtain a valid value for 'string'
  Cause: No valid value was obtained for this parameter.
  Action: Rerun the application and enter a valid value.

OCI-30120: 'string' is not a legal oracle number for 'string'
  Cause: The value is not a valid oracle number.
  Action: Refer to the manual for allowable oracle number values.

OCI-30121: 'string' is not an allowable value for 'string'
  Cause: The value is not a legal value for this parameter.
  Action: Refer to the manual for allowable values.

OCI-30122: value 'string' for 'string' must be between 'number' and 'number'
  Cause: The value of the parameter is not within the legal range.
  Action: Specify a value that is within the legal range.

OCI-30129: invalid function argument received
  Cause: A function received an invalid argument
  Action: Check function calls, make sure correct arguments are being passed.

OCI-30130: invalid parameter key type received
  Cause: A function received an invalid parameter key type
  Action: Check parameter key types in function calls

OCI-30131: number of keys being set exceeds allocation
  Cause: Number of parameter keys being set exceeds allocation
  Action: Reduce the number of keys being set or increase allocation

OCI-30132: invalid key index supplied
  Cause: The key index specified was not within bounds
  Action: Change key index to ensure it lies within bounds

OCI-30133: reserved for future use
  Cause: None.
  Action: None.

OCI-30134: reserved for future use
  Cause: None.
  Action: None.

OCI-30135: OCI Thread operation fails
  Cause: An OCI Thread function call has failed.
  Action: Check the function call to make sure that the correct parameters are being passed and take the apropriate action.

OCI-30150: Invalid argument passed to OCIFile function
  Cause: An invalid argument is passed to the OCIFile function. The most common cause is that a NULL pointer is passed where a non-NULL pointer is expected.
  Action: Make sure that the values passed as arguments are valid. Esp check for NULL pointers.

OCI-30151: File already exists
  Cause: Tried to open a file with OCI_FILE_EXCL flag and the file already exists.
  Action: OCIFile is supposed throw this exception in this case.

OCI-30152: File does not exist
  Cause: The OCIFile function requires the file to exist, but it does not.
  Action: Make sure that the file exists.

OCI-30153: An invalid File Object is passed to the OCIFile function
  Cause: An invalid File Object is passed to the OCIFile function.
  Action: Make sure that the file object is a valid one. Create a new file object by calling OCIFileOpen if needed.

OCI-30154: The memory address given as buffer for OCIFileRead/Write is invalid
  Cause: An invalid memory address is given as the buffer pointer for OCIFileRead/Write.
  Action: Make sure that the required memory is allocated and pass a valid memory address as buffer pointer.

OCI-30155: An I/O Error occured during an OCIFile function call
  Cause: An I/O error occurred at the system level.
  Action: This is a system error and the action will depnd on the error.

OCI-30156: Out of disk space
  Cause: The disks associated with the underlying file system are full.
  Action: Create more disk space.

OCI-30157: An invalid argument was given to operating system call
  Cause: The OS call was called with an invalid argument.
  Action: Check the values passed. If unsuccessful to solve the problem contact ORACLE support.

OCI-30158: The OCIFileWrite causes the file to exceed the maximum allowed size
  Cause: There is no space to write to the file. Its size is at the maximum limit.
  Action: Up to the user.

OCI-30159: OCIFileOpen: Cannot create the file or cannot open in the requested mode
  Cause: The create flag was specified in OCIFileOpen such that the file was to be created. But unable to do so. Or the file already exists and the permissions on it doesn't allow the file to be opened in in the requested open mode
  Action: Check whether the user has permissions to create the specified file or if the file exists whether the permissions on it allow the requested open mode.

OCI-30160: Unable to access the file
  Cause: The function was unable to access the existing the file.
  Action: Check if the user has the required permissions on the file.

OCI-30161: A system error occurred during the OCIFile function call
  Cause: A system error occured while executing the OCIFile function.
  Action: Depend on the error.

OCI-30162: The OCIFile context is not initialzed
  Cause: The function OCIFileInit need to be called before calling any other OCIFile function to initialize the OCIFile context.
  Action: Call the function OCIFileInit need to be called before calling any other OCIFile function.

OCI-30163: The thread safety initialization failed
  Cause: The call to SlgInit failed in OCIFileInit.
  Action: Contact support

OCI-30175: invalid type given for an argument
  Cause: There is an argument with an invalid type in the argument list.
  Action: Use the correct type wrapper for the argument.

OCI-30176: invalid format code used in the format string
  Cause: There is an invalid format code in the format string.
  Action: Replace the invalid format code with a valid one.

OCI-30177: invalid flag used in a format specification
  Cause: There is an invalid flag in a format specification.
  Action: Replace the invalid flag with a valid one.

OCI-30178: duplicate flag used in a format specification
  Cause: There is a duplicate flag in a format specification.
  Action: Remove the duplicate flag.

OCI-30179: invalid argument index used in a format code
  Cause: Zero or negative argument index or index not following (."
  Action: Replace the invalid argument index with a valid one.

OCI-30180: argument index is too large
  Cause: An argument index exceeds actual number of arguments supplied.
  Action: Fix format string or pass additional arguments.

OCI-30181: integer in argument index is not immediately followed by )
  Cause: Missing closing parenthesis in argument index.
  Action: Fix the format specification.

OCI-30182: invalid precision specifier
  Cause: Period in format specification not followed by valid format.
  Action: Replace the invalid precision specifier with a valid one.

OCI-30183: invalid field width specifier
  Cause: Invalid field width supplied.
  Action: Replace the invalid field width with a valid one.

OCI-30184: argument type not compatible with a format code
  Cause: Bad argument type given for a format code.
  Action: Make format and arguments be compatible.

OCI-30185: output too large to fit in the buffer
  Cause: The buffer is not large enough to hold the entire output string.
  Action: Fix the buffer size and length passed in.

OCI-30186: reserved for future use
  Cause: None.
  Action: None.

OCI-30187: reserved for future use
  Cause: None.
  Action: None.

OCI-30188: reserved for future use
  Cause: None.
  Action: None.

OCI-30189: reserved for future use
  Cause: None.
  Action: None.

OCI-30190: reserved for future use
  Cause: None.
  Action: None.

OCI-30191: missing argument list
  Cause: No argument list supplied.
  Action: Modify the argument list to have at least OCIFormatEnd in it.

OCI-30192: reserved for future use
  Cause: None.
  Action: None.

OCI-30193: reserved for future use
  Cause: None.
  Action: None.

OCI-30194: reserved for future use
  Cause: None.
  Action: None.

OCI-30195: reserved for future use
  Cause: None.
  Action: None.

OCI-30196: reserved for future use
  Cause: None.
  Action: None.

OCI-30197: reserved for future use
  Cause: None.
  Action: None.

OCI-30198: reserved for future use
  Cause: None.
  Action: None.

OCI-30199: reserved for future use
  Cause: None.
  Action: None.

OCI-30930: XML node 'string' (type=string) does not support this operation
  Cause: The given node's type is not supported for this operation. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.
  Action: Use a valid node type for the operation.

OCI-30931: Element 'string' cannot contain mixed text
  Cause: XML elements must be declared mixed to contain multiple text nodes
  Action: Declare this element type as mixed in its schema

OCI-30932: Reference node 'string' not contained in specified parent node 'string'
  Cause: When using a reference node, it must have the specified parent node
  Action: Use a node in the specified parent as the reference

OCI-30933: Element 'string' may not appear at this point within parent 'string'
  Cause: The ordering specified by the content model of the parent does not allow for this element to occur at this position.
  Action: Reorder the child elements to conform with the content model of the parent element

OCI-30934: 'string' (string node) cannot be inserted in parent 'string' (string node)
  Cause: The schema does not allow a child node of this type to be inserted into a parent node of this type. For example, only element nodes may only be inserted into a document
  Action: Insert only child nodes that make sense for this node type

OCI-30935: XML maxoccurs value (string) exceeded
  Cause: An attempt was made to insert more than maxoccurs values into a schema-based XML document.
  Action: Do not insert more than maxoccurs values into the document.

OCI-30936: Maximum number (string) of 'string' XML node elements exceeded
  Cause: An attempt was made to insert more than the allowed number of elements (specified by the maxoccurs facet) into an XML document.
  Action: Do not attempt to add more than the maximum number of elements to XML documents.

OCI-30937: No schema definition for 'string' (namespace 'string') in parent 'string'
  Cause: The schema definition for the parent node being processed does not allow for the specified child node in its content model. Note that any typecasting via xsi:type must occur before the schema definitions for the new type can be used.
  Action: Only insert elements and attributes declared in the schema. Check to make sure that xsi:type (if used) is specified first.

OCI-30938: No prefix defined for namespace 'string' (particle string)
  Cause: An XML namespace mapping (xmlns:<prefix>=<namespace URL>) must be defined for each particle (element or attribute) stored in an schema-constrained XMLType document.
  Action: Add an xmlns attribute definition (attribute name="xmlns:prefix" and value="namespace URL") to the current XMLType document. The safest place to add this attribute is in the root node of the document to ensure that the mapping will be in scope.

OCI-30939: Order violation: Element 'string' may not follow element 'string'
  Cause: The XML schema specifies a content model that is sequential, where the order of nodes in the instance must follow the order specified by the schema, and this instance relies on the schema validity to avoid maintaining instance order information
  Action: Insert elements only in the order specified in the schema

OCI-30940: Cannot resolve prefix 'string' for QName node 'string'
  Cause: An attempt was made to store a QName value without having a valid namespace in scope for that prefix.
  Action: Declare the namespace for the prefix used

OCI-30941: Cannot specify empty URI for non-default namespace 'string'
  Cause: An attempt was made to insert a namespace declaration for a non-default namespace using an empty URI string.
  Action: Specify a non-empty URI for namespace declarations other than the default namespace. ////// Errors 30942 to 30950 reserved for XML Schema Evolution

OCI-30942: XML Schema Evolution error for schema 'string' table string column 'string'
  Cause: The given XMLType table/column which conforms to the given schema had errors during evolution. For more information, see the more specific error below this one
  Action: Based on the schema, table and column information in this error and the more specific error below, take corrective action

OCI-30943: XML Schema 'string' is dependent on XML schema 'string'
  Cause: Not all dependent schemas were specified and/or the schemas were not specified in dependency order, i.e., if schema S1 is dependent on schema S, S must appear before S1.
  Action: Include the previously unspecified schema in the list of schemas and/or correct the order in which the schemas are specified. Then retry the operation.

OCI-30944: Error during rollback for XML schema 'string' table string column 'string'
  Cause: The given XMLType table/column which conforms to the given schema had errors during a rollback of XML schema evolution. For more information, see the more specific error below this one
  Action: Based on the schema, table and column information in this error and the more specific error below, take corrective action

OCI-30945: Could not create mapping table 'string'
  Cause: A mapping table could not be created during XML schema evolution. For more information, see the more specific error below this one
  Action: Ensure that a table with the given name does not exist and retry the operation

OCI-30946: XML Schema Evolution warning: temporary tables not cleaned up
  Cause: An error occurred after the schema was evolved while cleaning up temporary tables. The schema evolution was successful
  Action: If the user needs to remove the temporary tables, use the mapping table to get the temporary table names and drop them. ///// End of XML Schema Evolution errors (30942 to 30950 reserved)

OCI-30951: Element or attribute at Xpath string exceeds maximum length
  Cause: An attempt was made to insert a node of length exceeding the maximum length (specified by the maxLength facet) into an XML document.
  Action: Do not attempt to add a node exceeding the maximum length to XML documents.

OCI-30990: insufficient privileges to change owner of resource string
  Cause: An attempt was made to change the <Owner> field of an XML DB resource without sufficient privileges to do so.
  Action: Switch to SYS before performing the ownership change, or have the intended recipient of the resource perform the transfer.

OCI-30991: cannot use DOM to add special attribute to schema-based parent
  Cause: An attempt was made to add or remove an xsi:schemaLocation, xsi:noNamespaceSchemaLocation, xsi:type, or xsi:nil attribute to or from a schema-based XML node using DOM.
  Action: Use the updateXML operator instead of DOM.

OCI-31000: Resource 'string' is not an XDB schema document
  Cause: The given schema URL does not refer to a registered XDB schema
  Action: Make sure the specified schema has been registered in XDB

OCI-31001: Invalid resource handle or path name "string"
  Cause: An invalid resource handle or path name was passed to the XDB hierarchical resolver.
  Action: Pass a valid resouce handle or path name to the hierarchical resolver.

OCI-31002: Path name string is not a container
  Cause: XDB expected the given path name to represent a container.
  Action: Pass a path name or resource handle that represents a container.

OCI-31003: Parent string already contains child entry string
  Cause: An attempt was made to insert a duplicate child into the XDB hierarchical resolver.
  Action: Insert a unique name into the container.

OCI-31004: Length string of the BLOB in XDB$H_INDEX is below the minimum string
  Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must have a certain minimum length without being chained. The calculated length of the LOB was less than the stated minimum.
  Action: Set the value of the init.ora parameter db_block_size to at least 2K. For XDB to run at its fastest, set db_block_size to 8K.

OCI-31005: Path name length string exceeds maximum length string
  Cause: The length of a path name passed to the XDB hierarchical resolver exceeded the maximum length.
  Action: Choose a shorter path name.

OCI-31006: Path name segment length string exceeds maximum length string
  Cause: The length of a path name segment passed to the XDB hierarchical resolver exceeded the maximum length of a path name segment.
  Action: Choose a shorter path name segment.

OCI-31007: Attempted to delete non-empty container string/string
  Cause: An attempt was made to delete a non-empty container in the XDB hierarchical resolver.
  Action: Either perform a recursive deletion, or first delete the contents of the container.

OCI-31009: Access denied for property string
  Cause: An attempt was made to access a property you don't have access to
  Action: Check the ACL to see what privileges you have for this property

OCI-31010: XML element index string exceeds maximum insertion index string
  Cause: An attempt was made to insert an XML element at an invalid index location in the node.
  Action: Choose a new index that falls within the allowed range.

OCI-31011: XML parsing failed
  Cause: XML parser returned an error while trying to parse the document.
  Action: Check if the document to be parsed is valid.

OCI-31012: Given XPATH expression not supported
  Cause: XPATH expression passed to the function is currently unsupported.
  Action: Check the xpath expression and change it to use a supported expression.

OCI-31013: Invalid XPATH expression
  Cause: XPATH expression passed to the function is invalid.
  Action: Check the xpath expression for possible syntax errors.

OCI-31014: Attempted to delete the root container
  Cause: An attempt was made to delete the root container in the hierarchical index.
  Action: Do not delete the root container.

OCI-31015: Attempted to insert entry without name
  Cause: An attempt was made to insert an entry into the hierarchical resolver without a child name.
  Action: Supply a child name and try inserting again.

OCI-31016: Attempted to delete entry without name
  Cause: An attempt was made to delete an entry from the hierarchical resolver without a child name.
  Action: Supply a child name and try deleting again.

OCI-31017: Error generating unique OID for XML document
  Cause: An error occurred while generating a globally unique OID for storing an XML document.
  Action: none

OCI-31018: Error deleting XML document
  Cause: The XMLType object pointed to by the given REF could not be deleted because either the REF was invalid or it pointed to a non-existent table.
  Action: Either use FORCE deletion or supply a valid REF.

OCI-31019: Recursive deletion snapshot too old for string/string
  Cause: Changes were made to the structure of a directory while it was being recursively deleted.
  Action: Try deleting the directory again.

OCI-31020: The operation is not allowed, Reason: string
  Cause: The operation attempted is not allowed
  Action: See reason and change to a valid operation.

OCI-31021: Element definition not found
  Cause: The element definition was not found.
  Action: Supply the definition for the element or use a defined element.

OCI-31022: Element not found
  Cause: The element was not found.
  Action: Make sure the specified element exists.

OCI-31023: Index size error
  Cause: The index is greater than the allowed value.
  Action: Make sure the index is less than allowed value.

OCI-31025: Invalid document element
  Cause: An attempt was made to replace the data at an invalid index number in the XML document
  Action: Supply a correct occurrence number and try again.

OCI-31027: Path name or handle string does not point to a resource
  Cause: An attempt was made to retrieve a resource based on a path name or resource handle that points to an entity other than a resource.
  Action: Do not attempt to retrieve a resource based on that path name or resource handle.

OCI-31028: Resource metadata length string exceeded maximum length string
  Cause: An attempt was made to insert resource metadata that exceeded the maximum length of that type of metadata.
  Action: Keep resource metadata within its allowed length.

OCI-31029: Cannot bind to unsaved resource
  Cause: An attempt was made to bind to a resource that had not been saved to disk.
  Action: Bind only to saved resources.

OCI-31030: Unable to retrieve XML document
  Cause: The resource had an invalid (dangling) REF to an XML document.
  Action: Rebind the resource using a valid XMLType REF.

OCI-31033: Requested number of XML children string exceeds maximum string
  Cause: An attempt was made to add more than the maximum number of allowable children in an XML element.
  Action: Redefine the schema to allow breaking up of the children among siblings.

OCI-31035: Could not bind locked resource to path string/string
  Cause: An attempt was made to bind an existing resource to a new location in the hierarchy, but a lock could not be obtained on the resource.
  Action: Commit or roll back the transaction that has the lock on the resource.

OCI-31037: Invalid XML attribute name string
  Cause: The attribute name in the XML document did not match anything in the associated schema.
  Action: Supply only schema-defined or XML standard attributes.

OCI-31038: Invalid string value: "string"
  Cause: The text in the XML document did not represent a valid value given the datatype and other constraints in the schema.
  Action: Ensure that the specified value in XML documents is valid with respect to the datatype and other constraints in the schema.

OCI-31039: XML namespace length string exceeds maximum string
  Cause: The length of the disk-formatted XML namespace exceeded the maximum.
  Action: Keep XML namespace declarations below the maximum length.

OCI-31040: Property string: XML type (string) not compatible with internal memory type (string)
  Cause: The XML datatype given is inconsistent with the database datatype, and a conversion cannot be made.
  Action: This is an internal error, generally resulting from corruption of the compiled XML schema. Re-register schemas, or contact Oracle support.

OCI-31041: Property string: Memory type (string) not compatible with database type (string)
  Cause: The memory type associated with this property is mapped to an incompatible database type, and a conversion cannot be made.
  Action: This is an internal error, generally resulting from corruption of the compiled XML schema. Re-register schemas, or contact Oracle support.

OCI-31042: Too many properties in type 'string'
  Cause: The type can only have the same number of properties (elements and attributes) as a table can have columns.
  Action: Modify the XML schema to move properties into subelements that are not inlined.

OCI-31043: Element 'string' not globally defined in schema 'string'
  Cause: The specified element name has not been defined at the top level of the XML schema (i.e. globally). Elements must be defined globally to be the root of an XMLType object.
  Action: Check the XML schema definition to make sure the specified element name has been defined at the top level.

OCI-31044: Top-level prefix length string exceeds maximum string
  Cause: An attempt was made to save to disk a top-level XML namespace prefix whose length exceeded the maximum.
  Action: Do not define XML namespace prefixes that exceed the maximum length.

OCI-31045: Cannot store more than string extras outside the root XML node
  Cause: An attempt was made to store more than the maximum number of XML extras (e.g. comments and processing instructions) either before or after the document's root node.
  Action: Keep the number of extras outside the root node below the maximum.

OCI-31046: Incorrect argument(s) specified in the operator
  Cause: One or more of the arguments specified in the operator in the query are incorrect
  Action: Correct the arguments specified in the operator

OCI-31047: Could not retrieve resource data at path string
  Cause: An error occurred while retrieving the contents and/or metadata of a resource.
  Action: Contact Oracle customer support.

OCI-31048: Unsaved resources cannot be updated
  Cause: An attempt was made to update a resource that was never saved to disk.
  Action: Perform a resource insertion instead.

OCI-31050: Access denied
  Cause: The requested access privileges have not been granted to the current user. User must be granted privileges prior to resource access.
  Action: Check the set of requested access privileges to make sure that they are included in the set of access privilges granted to the user.

OCI-31051: Requested access privileges not supported
  Cause: The requested access privileges are not supported for the specified resource.
  Action: Ensure that the set of requested access privileges are valid access privileges for the specified resource.

OCI-31052: Cannot delete ACL with other references
  Cause: The requested deletion of an ACL resource cannot proceed. The ACL is in use by other resources.
  Action: Remove the resources that are making reference to the ACL in question and try again.

OCI-31053: The value of the depth argument in the operator cannot be negative
  Cause: The value of the depth argument passed to the primary operator is not a positive integer
  Action: Pass a positive value of the depth argument

OCI-31054: The string operator cannot have an ancillary operator
  Cause: An ancillary operator was used with an operator which does not does not support ancillary operators
  Action: Remove the ancillary operator in the query

OCI-31055: A null XMLType element cannot be inserted into RESOURCE_VIEW
  Cause: The element which is being inserted into the RESOURCE_VIEW is NULL
  Action: Specify a non-null XMLType element to insert into RESOURCE_VIEW

OCI-31056: The document being inserted does not conform to string
  Cause: The XMLType element being inserted into the RESOURCE_VIEW does not conform to the specified Schema
  Action: Insert an element which conforms to the specified Schema

OCI-31057: Display Name of the element being inserted is null
  Cause: The Display Name of the element which is being inserted into the RESOURCE_VIEW is null
  Action: Specify the Display Name and insert the element into RESOURCE_VIEW

OCI-31058: cannot modify read-only XOBs
  Cause: Read-Only XOBs cannot be modified.
  Action: Use only read operations on such a XOB.

OCI-31059: Cannot insert root XML document node if it already exists
  Cause: An attempt was made to insert a root node into an XML document that already had a root node.
  Action: Call the appropriate replace function to replace the node instead of inserting it anew.

OCI-31060: Resource at path string could not be deleted
  Cause: An error occurred while deleting the named resource. The specific error can be found one lower on the error stack.
  Action: Look at the next error on the stack and take approprate action.

OCI-31062: Cannot delete an unsaved resource
  Cause: An attempt was made to delete a resource that had not been saved to disk.
  Action: Delete only saved resources.

OCI-31065: Cannot modify read-only property [string]
  Cause: An attempt was made to modify an immutable XML node.
  Action: Use only read operations on such properties.

OCI-31066: Insertion of string into string creates a cycle
  Cause: An attempt was made to insert a link into the XDB hierarchy that would create a cycle in the tree.
  Action: Ensure that links to existing resources do not cause cycles.

OCI-31067: XML nodes must be updated with nodes of the same type
  Cause: An attempt was made to use updateXML to update an XML node with a node of another type.
  Action: Ensure that the node specified by the XPath matches the type of new data provided.

OCI-31068: updateXML expected data format [string] instead of [string]
  Cause: An attempt was made to use updateXML to update data with a node of the incorrect type. Text and attribute nodes must be updated with string data, whereas element nodes must be updated with XMLType data.
  Action: Use CREATEXML or getStringVal to coerce the new data to the proper format.

OCI-31069: Cannot apply typed changes to non-schema-based XMLType nodes
  Cause: An attempt was made to insert, delete, or update a non-schema-based XMLType node using an XML schema definition.
  Action: Make changes to non-typed nodes only by referencing their tag names.

OCI-31070: Invalid database user ID string
  Cause: An attempt was made set an invalid user ID into an XDB resource metadata property.
  Action: Verify the validity of the user ID and try again.

OCI-31071: Invalid database username or GUID string
  Cause: An attempt was made to set an invalid username or GUID into an XDB resource metadata property.
  Action: Verify the validity of the username or GUID and try again.

OCI-31072: Too many child nodes in XMLType fragment for updateXML
  Cause: An attempt was made to pass an XMLType fragment with multiple children as new data for the updateXML operator.
  Action: Extract the desired child from the XMLType before passing it to updateXML as the desired new XML node.

OCI-31073: Resource not retrieved using path name
  Cause: An attempt was made to access the path name of a resource that was either never saved to disk or was loaded using a method other than with its path name.
  Action: Perform path name operations only on resources obtained using a path name. ////// 31075 - 31099 reserved for XML Schema Compiler

OCI-31075: invalid string declaration in XML Schema
  Cause: The XML schema contains an invalid declaration identified by the message.
  Action: Fix the identified error and try again.

OCI-31076: required attribute "string" not specified
  Cause: The XML schema does not specify a required attribute.
  Action: Specify a value for the required attribute.

OCI-31077: invalid attribute "string" specified
  Cause: The XML schema specifies an invalid attribute.
  Action: Remove specification of the invalid attribute.

OCI-31078: error in SQL mapping information
  Cause: There is an error in the SQL type and table specification within the XML Schema.
  Action: Ensure that all specified SQL types and tables are valid and compatible with the corresponding XML types.

OCI-31079: unable to resolve reference to string "string"
  Cause: The identified type or attribute or element could not be resolved.
  Action: Make sure that the name corresponds to a valid XML (simple/complex) type or attribute or element and try again.

OCI-31080: type not specified for attribute or element "string"
  Cause: The identified attribute or element does not have a type.
  Action: Make sure that every attribute and element has a valid type specification.

OCI-31081: name not specified for global declaration
  Cause: The XML schema does not specify the name for the global declaration of attribute or element or simpleType or complexType.
  Action: Specify names for all global declarations.

OCI-31082: invalid attribute "string" specified in declaration of "string"
  Cause: The XML schema specifies an invalid attribute.
  Action: Remove specification of the invalid attribute.

OCI-31083: error while creating SQL type "string"."string"
  Cause: An error occurred while trying to create the SQL type based on the specification of a complex type.
  Action: Fix the identified error and try again.

OCI-31084: error while creating table "string"."string" for element "string"
  Cause: An error occurred while trying to create the table based on the declaration for the identified element.
  Action: Fix the identified error and try again.

OCI-31085: schema "string" already registered
  Cause: An attempt was made to register a schema with the same URL as a previously registered schema.
  Action: Register the schema with a different URL.

OCI-31086: insufficient privileges to register global schema "string"
  Cause: An attempt was made to register a global schema without sufficient privileges.
  Action: Make sure that the user has sufficient privileges to register a global schema.

OCI-31087: insufficient privileges to delete schema "string"
  Cause: An attempt was made to delete a schema resource without sufficient privileges.
  Action: Make sure that the user has sufficient privileges to delete the schema.

OCI-31088: object "string"."string" depends on the schema
  Cause: An attempt was made to delete a schema which has dependent objects.
  Action: Either drop the dependent objects prior to deleting the schema or use the CASCADE or FORCE options.

OCI-31089: schema "string" does not target namespace "string"
  Cause: The schema document contains references (via include and import definitions) to other schemas that do not belong to valid namespaces.
  Action: Make sure that all schemas referenced via include definitions target the same namespace as the parent schema. Further make sure that the namespace specified in the import definition matches the actual target namespace of the specified schema.

OCI-31090: invalid database schema name "string"
  Cause: The XML schema document contains an invalid database schema name For example, the value of attribute SQLSchema
  Action: Make sure that all database user/schema names specified in the XML schema document refer to existing database users/schemas.

OCI-31091: empty string specified as a SQL name
  Cause: The XML schema document contains a null SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.
  Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. Otherwise, remove such attributes from the schema and try again.

OCI-31092: invalid SQL name "string"
  Cause: The XML schema document contains an invalid SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.
  Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. This implies that the database length and other restrictions on names be satisfied.

OCI-31093: null or invalid value specified for parameter : string
  Cause: The argument value passed for the given parameter is null or invalid.
  Action: Make sure that all the input argument values are valid.

OCI-31094: incompatible SQL type "string" for attribute or element "string"
  Cause: The SQL type information provided in the XML schema is not compatible with the XML datatype for the specified attribute or element.
  Action: Make sure that the specified SQL types are compatible with the declared XML datatypes.

OCI-31095: cannot generate string : "string.string" already exists
  Cause: The type/table name specified in the XML schema document cannot be generated because it is already being used.
  Action: Use different names for types/tables or use the NOGEN mode so that schema compiler does not generate new types/tables.

OCI-31096: validation failed for schema
  Cause: The XML Schema could not be validated.
  Action: Make sure that the SQLType and other datatype mapping is valid.

OCI-31097: Hierarchical Index not empty
  Cause: An attempt was made to rebuild the hierarchical index which is not empty.
  Action: Delete all rows in the hierarchical index and then rebuild it.

OCI-31099: XDB Security Internal Error
  Cause: An XDB Security internal error has occurred.
  Action: Contact Oracle Support. ////// 31100 - 31110 reserved for WebDAV compliant resource locks

OCI-31100: XDB Locking Internal Error
  Cause: An XDB Locking Internal error has occurred.
  Action: Contact Oracle Support.

OCI-31101: Token "string" not given while locking resource "string"
  Cause: Locking attempted on resource when the pricipal already owns a lock given by the token above.
  Action: Reattempt the lock with the token.

OCI-31102: Already locked in exclusive mode. Cannot add lock.
  Cause: The resource is already locked in exclusive mode. Cannot add another lock.
  Action: Unlock the existing lock.

OCI-31103: Resource locked in shared mode. Cannot add exclusive lock
  Cause: The resource is locked in shared mode. Cannot add a shared lock.
  Action: Try locking in shared mode or unlocking the existing lock.

OCI-31104: Cannot find lock with token "string" on "string" for unlock
  Cause: The lock may have been unlock or it may have expired.
  Action: No action needed. Unlock already successful.

OCI-31105: User does not own lock "string"
  Cause: The lock to be unlocked is not owned by the user.
  Action: none

OCI-31107: Action failed as resource "string" is locked by name lock
  Cause: Lock requests cause the whole request URI to be locked
  Action: Supply lock token or unlock the lock

OCI-31108: Action failed as resource string is locked
  Cause: Delete/Rename failed because of an existing lock
  Action: Do lockdiscovery to find the lock and delete it.

OCI-31109: Action failed as parent resource string is locked
  Cause: Delete/Rename failed because of an lock on parent resource
  Action: Do lockdiscovery to find the lock and delete it.

OCI-31110: Action failed as resource string is locked by name
  Cause: Delete/Rename failed because one of the children is locked.
  Action: Do lockdiscovery to find the lock and delete it.

OCI-31111: table string cannot be hierarchically enabled
  Cause: Trigger <tabname>_xdb_pitrigger already exists
  Action: Delete all rows in the hierarchical index and then rebuild it.

OCI-31112: fail to string for string port using xdb configuration
  Cause: port number for the defined presentation is not valid
  Action: Either the port number is already in use or it is protected. Specify another port number.

OCI-31113: XDB configuration may not be updated with non-schema compliant data
  Cause: An attempt was made to update the XDB configuration resource with non-schema or non-schema compliant data.
  Action: Check the document to make sure it is schema based and schema compliant.

OCI-31114: XDB configuration has been deleted or is corrupted
  Cause: The XDB configuration resource has been deleted or corrupted.
  Action: Reinstall XDB, or reinsert a valid configuration document.

OCI-31115: XDB configuration error: string
  Cause: An error related to XDB configuration has occurred.
  Action: Make sure the configuration resource contains valid data.

OCI-31116: Tablespace not specified correctly
  Cause: XDB cannot be moved to the specified tablespace.
  Action: Specify a valid tablespace.

OCI-31121: The string operator can not be FALSE
  Cause: The value of the operator that is specified is FALSE
  Action: Specify an operator that evaluates to TRUE

OCI-31122: The string operator has incorrect RHS value
  Cause: The right hand side value that has been specified for the operator does not evaluate to TRUE
  Action: Specify value on the right hand side that evaluate to TRUE ////// 31151 - 31189 reserved for XML Schema Compiler

OCI-31151: Cyclic definition encountered for string: "string"
  Cause: The schema definition for this type has cycles.
  Action: Remove cyclic definition and re-compile schema.

OCI-31153: Cannot create schema URL with reserved prefix "http://xmlns.oracle.com/xdb/schemas/"
  Cause: This prefix is reserved for XDB extended schema URLs and cannot be used in a user specified URL.
  Action: Modify the prefix to a different one.

OCI-31154: invalid XML document
  Cause: The XML document is invalid with respect to its XML Schema.
  Action: Fix the errors identified and try again.

OCI-31155: attribute string not in XDB namespace
  Cause: The specified attribute should be prefixed with XDB's namespace.
  Action: Ensure that all XDB specified attributes are prefixed with XDB's namespace and try again.

OCI-31157: Invalid Content-Type charset
  Cause: HTTP Content-Type header had a charset that Oracle does not understand.
  Action: Fix the Content-Type header in the HTTP request.

OCI-31158: schema "string" currently being referenced
  Cause: The specified schema URL is currently being referenced by the same session. This could happen because of PLSQL XMLType variables still in scope.
  Action: Ensure all references to this schema in this session are released and try the operation again.

OCI-31159: XML DB is in an invalid state
  Cause: XML DB's internal tables are in an invalid state, probably because the database was not upgraded or the upgrade was not successful
  Action: Ensure that the database is upgraded successfully. If the problem persists, contact Oracle Support

OCI-31160: max substitution group size string exceeded by "string" (string) for head element "string" (string)
  Cause: The maximum limit on nested substitution groups has been exceeded by an element.
  Action: Delete specified schema and re-register it after removing the offending substitution element.

OCI-31161: element or attribute "string" cannot be stored out of line
  Cause: An element or attribute of a simple type has SQLInline=false
  Action: Remove the SQLInline=false qualification for the offending element or attribute

OCI-31162: element or attribute "string" has no SQLType specified
  Cause: Schema registration was invoked with GENTYPES=false without specifying a SQLType for some element or attribute
  Action: Specify a SQLType for the offending element or attribute and register the schema again

OCI-31163: element or attribute "string" has invalid attribute value "string" (should be "string")
  Cause: An element or attribute for a complextype derived by restriction has an attribute whose value is different from that in the base type
  Action: Remove the mismatched attribute values from the offending element or attribute

OCI-31164: cannot load object-relational XML attribute using direct path
  Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column contains a type with subtypes. This type of attribute cannot be loaded with direct path.
  Action: Perform the load with conventional path mode.

OCI-31165: cannot load object-relational XML attribute using direct path
  Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column either contains an out-of-line partitioned table or the table itself is partitioned by one of the attributes of xmltype. This type of table cannot be loaded with direct path.
  Action: Perform the load with conventional path mode.

OCI-31167: XML nodes over 64K in size cannot be inserted
  Cause: An attempt was made to insert an XML Text Node with a size greater than 64K. This is not supported.
  Action: Create text nodes under 64K.

OCI-31168: Node localname and namespace values should be less than 64K
  Cause: An attempt was made to specify an XML Node with localname or namespace value greater than or equal to 64K. This is not supported.
  Action: Node localnames and namespace values should be under 64K. ////// 31180 - 31189 reserved for PL/SQL DOM API

OCI-31180: DOM Type mismatch in invalid PL/SQL DOM handle
  Cause: The specified PL/SQL DOM handle is referencing a DOM Node whose DOM Type that does not match the one available in the session. This could happen because the pl/sql handle was reused, or the original document is no longer available.
  Action: Ensure that the pl/sql handle for the target node is valid and try the operation again.

OCI-31181: PL/SQL DOM handle accesses node that is no longer available
  Cause: The specified pl/sql handle is referencing a node in a DOM Document that is no longer available.
  Action: Ensure that the pl/sql handle for the target node is valid and try the operation again.

OCI-31182: Too many PL/SQL DOM handles specified
  Cause: An attempt was made to create a PL/SQL DOM handle that exceeded the maximum allowable number of PL/SQL DOM handles.
  Action: Free PL/SQL DOM handles and try the operation again.

OCI-31185: DOM Nodes do not belong to the same DOM Document
  Cause: The specified PL/SQL DOM Node does not belong to the parent DOM Document of the referring DOM Node.
  Action: Ensure that both the DOM Nodes are part of the same DOM Document.

OCI-31190: Resource string is not a version-controlled resource
  Cause: Either one of the following is the cause:

  - Checkout is requested for a resource that isn't under version control". Only version-controlled resource can be checked out.

  - Checkout is requested for a row of a non-versioned table.

  Action: put the resource under version-control before checking out.

OCI-31191: Resource string is already checked out
  Cause: Either one of the following is the cause:

  - Checkout is requested for a resource that is already checked out to the workspace by the same of different user.

  Action: checked in the resource from the workspace before checking out

OCI-31192: Resource string has not been checked out
  Cause: Either one of the following is the cause:

  - Checkin or uncheckout is requested for a resource that has not been checked out to the workspace by any user in a workspace

  Action: checked in the resource from the workspace before checking out

OCI-31193: This versioning feature isn't supported for resource string
  Cause: Either one of the following is the cause:

  - Container cannot be put under version-controlled.

  Action: Avoid using these features.

OCI-31194: Resource string is already deleted
  Cause: Access a version-controlled resource that is already deleted.
  Action: Remove the cyclic definitions in the type and retry compilation.

OCI-31195: XML node 'string' (type=string) does not support this operation
  Cause: The given node's type is not supported for this operation. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.
  Action: Use a valid node type for the operation.

OCI-31196: XML nodes over string in size cannot be printed
  Cause: An attempt was made to use an XML Text Node with a size greater than 64K, or an XML Comment Node with a size greater than 4K. These cannot be printed. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.
  Action: Use getClobVal() or getStringVal() to print the Document.

OCI-31197: Error in processing file string
  Cause: An error occurred while operating on the specifed file. The possible causes are the file header is corrupt or check the next error on stack
  Action: Ensure that the specified file is correct. Look at the next error on the stack and take appropriate action.

OCI-31198: Mismatch in number of bytes transferred due to non-binary mode
  Cause: An error occurred while reading the specifed file. The most probable cause is that the transfer was initiated in ASCII mode.
  Action: Ensure that the transfer mode is set to BINARY

OCI-31199: Warning in processing file string
  Cause: A warning was raised while operating on the specifed file. However, the current operation was completed successfully.
  Action: This is primarily an informational message. Look at the next error on the stack to obtain further information.